velodrome-v2

Swap tokens and manage classic AMM (volatile/stable) LP positions on Velodrome V2, the largest DEX on Optimism.

Highlights

• Token swaps via Router with automatic pool selection (volatile/stable)
• Get swap quotes without executing transactions
• Add and remove liquidity to volatile and stable AMM pools
• View LP token balances and positions across common pools
• Claim VELO gauge emissions and rewards
• Query pool information including reserves and addresses
• Support for major Optimism tokens (WETH, USDC, VELO, OP, etc.)
• Two-step confirmation process for all write operations

velodrome-v2 -- Skill Summary

Overview

This skill provides comprehensive access to Velodrome V2's classic AMM functionality on Optimism, enabling token swaps, liquidity management, and rewards claiming. It supports both volatile (constant-product) and stable (low-slippage) pools, with automatic pool selection for optimal routing. All write operations use a secure two-step confirmation process through the onchainos wallet system.

Usage

Ensure onchainos CLI is installed and your wallet is configured. Run commands first without --confirm to preview transactions, then add --confirm to broadcast. The velodrome-v2 binary must be available in your PATH.

Commands

• quote - Get swap quotes without executing transactions
• swap - Execute token swaps via Router (requires --confirm)
• pools - Query pool information and reserves
• positions - View LP token balances and positions
• add-liquidity - Add liquidity to pools (requires --confirm)
• remove-liquidity - Remove liquidity from pools (requires --confirm)
• claim-rewards - Claim VELO gauge emissions (requires --confirm)

Triggers

Activate this skill when users want to swap tokens, manage liquidity positions, or claim rewards on Velodrome V2's classic AMM pools on Optimism. Use for DeFi operations involving WETH, USDC, VELO, and other major Optimism tokens.

## Pre-flight Dependencies (auto-injected by Plugin Store CI)

> Run once per session before first use. These checks ensure required tools are installed.

### Install onchainos CLI + Skills (auto-injected)

```bash
# 1. Install onchainos CLI
onchainos --version 2>/dev/null || curl -fsSL https://raw.githubusercontent.com/okx/onchainos-skills/main/install.sh | sh

# 2. Install onchainos skills (enables AI agent to use onchainos commands)
npx skills add okx/onchainos-skills --yes --global

# 3. Install plugin-store skills (enables plugin discovery and management)
npx skills add okx/plugin-store --skill plugin-store --yes --global

Install velodrome-v2 binary (auto-injected)

if ! command -v velodrome-v2 >/dev/null 2>&1; then
  OS=$(uname -s | tr A-Z a-z)
  ARCH=$(uname -m)
  case "${OS}_${ARCH}" in
    darwin_arm64)  TARGET="aarch64-apple-darwin" ;;
    darwin_x86_64) TARGET="x86_64-apple-darwin" ;;
    linux_x86_64)  TARGET="x86_64-unknown-linux-gnu" ;;
    linux_aarch64) TARGET="aarch64-unknown-linux-gnu" ;;
  esac
  curl -fsSL "https://github.com/okx/plugin-store/releases/download/plugins/velodrome-v2@0.1.0/velodrome-v2-${TARGET}" -o ~/.local/bin/velodrome-v2
  chmod +x ~/.local/bin/velodrome-v2
fi

Report install (auto-injected, runs once)

REPORT_FLAG="$HOME/.plugin-store/reported/velodrome-v2"
if [ ! -f "$REPORT_FLAG" ]; then
  mkdir -p "$HOME/.plugin-store/reported"
  # Device fingerprint → SHA256 → 32-char device ID
  DEV_RAW="$(hostname):$(uname -s):$(uname -m):$HOME"
  DEV_ID=$(echo -n "$DEV_RAW" | shasum -a 256 | head -c 32)
  # HMAC signature (obfuscated key, same as CLI binary)
  _K=$(echo 'OE9nNWFRUFdfSVJkektrMExOV2RNeTIzV2JibXo3ZWNTbExJUDFIWnVoZw==' | base64 -d 2>/dev/null || echo 'OE9nNWFRUFdfSVJkektrMExOV2RNeTIzV2JibXo3ZWNTbExJUDFIWnVoZw==' | openssl base64 -d)
  HMAC_SIG=$(echo -n "${_K}${DEV_ID}" | shasum -a 256 | head -c 8)
  DIV_ID="${DEV_ID}${HMAC_SIG}"
  unset _K
  # Report to Vercel stats
  curl -s -X POST "https://plugin-store-dun.vercel.app/install" \
    -H "Content-Type: application/json" \
    -d '{"name":"velodrome-v2","version":"0.1.0"}' >/dev/null 2>&1 || true
  # Report to OKX API (with HMAC-signed device token)
  curl -s -X POST "https://www.okx.com/priapi/v1/wallet/plugins/download/report" \
    -H "Content-Type: application/json" \
    -d '{"pluginName":"velodrome-v2","divId":"'"$DIV_ID"'"}' >/dev/null 2>&1 || true
  touch "$REPORT_FLAG"
fi

</details>

---
*Generated by Plugin Store CI after maintainer approval.*

Summary: This plugin provides a binary CLI tool for interacting with Velodrome V2's classic AMM (volatile/stable pools) on Optimism. It supports token swaps, swap quotes, pool queries, LP position viewing, adding/removing liquidity, and claiming gauge rewards. Read operations use direct JSON-RPC eth_call to a public Optimism RPC, while write operations are routed through onchainos wallet contract-call.

Target Users: DeFi users and AI agents wanting to interact with Velodrome V2 on Optimism for swapping, liquidity provision, and reward management.

Components:

• Skill (SKILL.md)
• Binary (Rust source in src/, builds to velodrome-v2)

Skill Structure:
SKILL.md contains: metadata header, architecture description, data boundary notice, pre-flight checks, pool types table, 7 command sections (quote, swap, pools, positions, add-liquidity, remove-liquidity, claim-rewards) with examples and flow descriptions, supported token symbols table, contract addresses, error handling table, skill routing, and security notices. Well-structured with clear command documentation.

Data Flow:

1. Read-only operations (quote, pools, positions): Binary makes direct eth_call JSON-RPC requests to optimism-rpc.publicnode.com to query Velodrome V2 smart contracts (Router, PoolFactory, Voter, Pool, Gauge)
2. Write operations (swap, add-liquidity, remove-liquidity, claim-rewards): Binary constructs ABI-encoded calldata locally, then invokes onchainos wallet contract-call as a subprocess to handle signing and broadcasting via TEE
3. Wallet resolution: Uses onchainos wallet addresses to resolve the user's wallet address

Dependencies:

• External RPC: optimism-rpc.publicnode.com (public Optimism JSON-RPC endpoint)
• onchainos CLI: Used for wallet address resolution and transaction signing/broadcasting
• Rust crates: clap, tokio, reqwest, serde, serde_json, anyhow, hex (all well-known, reputable crates)

onchainos Commands Used

Wallet Operations

External APIs / URLs

Chains Operated On

• Optimism (Chain ID 10) — hardcoded throughout the plugin

Overall Permission Summary

This plugin reads on-chain data (pool reserves, balances, allowances, quotes) via direct RPC calls to a public Optimism node. All on-chain write operations (token approvals, swaps, adding/removing liquidity, claiming rewards) are delegated to onchainos wallet contract-call, which handles TEE signing and broadcasting. The plugin constructs ABI-encoded calldata locally and passes it to onchainos. It has significant financial operation capability including token swaps and liquidity management. The --force flag is used on contract calls, and there is a --confirm flag mechanism for user confirmation before broadcasting.

Does this plugin use onchainos CLI for all on-chain write operations?

Yes — All blockchain write operations are executed through onchainos wallet contract-call.

On-Chain Write Operations (MUST use onchainos)

Data Queries (allowed to use external sources)

External APIs / Libraries Detected

• reqwest HTTP client for JSON-RPC calls to optimism-rpc.publicnode.com
• No web3 libraries (ethers.js, web3.py, etc.) — raw ABI encoding is done manually
• No direct RPC write operations (eth_sendTransaction, eth_sendRawTransaction) — all writes go through onchainos

Verdict: ✅ Fully Compliant

The plugin correctly separates read operations (direct RPC eth_call) from write operations (onchainos wallet contract-call). All on-chain write operations use onchainos CLI as required.

Static Rule Scan (C01-C09, H01-H09, M01-M08, L01-L02)

LLM Judge Analysis (L-PINJ, L-MALI, L-MEMA, L-IINJ, L-AEXE, L-FINA, L-FISO)

Toxic Flow Detection (TF001-TF006)

TF006 check (M07/M08 + H05): M07 is satisfied (boundary declaration present). M08 is partially satisfied (field enumeration in Display sections). H05 is triggered (financial operations). Since M07 passes and M08 is downgraded to INFO, TF006 is NOT triggered.

No toxic flows detected.

Prompt Injection Scan

• No instruction overrides or identity manipulation
• No hidden behavior or confirmation bypasses in SKILL.md
• No base64-encoded content or invisible characters
• No pseudo-system tags
• Clear, straightforward documentation

Result: ✅ Clean

Dangerous Operations Check

The plugin involves: token approvals (unlimited — u128::MAX), swaps, liquidity management, and reward claiming. These are high-impact financial operations.

Confirmation mechanisms:

• --confirm flag required for broadcasting (without it, preview only)
• SKILL.md explicitly instructs "Ask user to confirm" before each write operation
• --dry-run flag available for simulation
• onchainos wallet contract-call provides additional TEE signing layer

Concern: Token approvals use u128::MAX (unlimited approval) which is noted in the source code (build_approve_calldata(router, u128::MAX)). While common in DeFi, SKILL.md does not warn about unlimited approvals.

Result: ⚠️ Review Needed — Unlimited approvals should be warned about explicitly.

Data Exfiltration Risk

• RPC calls only go to optimism-rpc.publicnode.com (read-only eth_call)
• No data is sent to any other external endpoint
• Binary output goes to stdout (consumed by agent)
• No file system writes beyond normal operation

Result: ✅ No Risk

Overall Security Rating: 🟡 Medium Risk

The plugin handles significant financial operations (swaps, liquidity management) but correctly delegates all signing to onchainos. The main concerns are: unlimited token approvals without user warning, and the use of --force on onchainos contract calls.

Language & Build Config

• Language: Rust (edition 2021)
• Entry point: src/main.rs
• Binary name: velodrome-v2

Dependency Analysis

All dependencies are well-known, widely-used Rust crates with no known vulnerabilities. No suspicious or unmaintained dependencies.

Code Safety Audit

Does SKILL.md accurately describe what the source code does?

Yes — The SKILL.md accurately describes the 7 commands, their parameters, the two-step confirmation flow, the use of onchainos for write operations, and the direct RPC for read operations. The contract addresses match. The flow descriptions match the code.

Minor discrepancy: SKILL.md says "3-second delay after approve" for swap but code shows 3 seconds; for add-liquidity SKILL.md says "5-second delay" and code shows 5 seconds — these match. SKILL.md mentions --confirm flag for write operations which is present in code.

Verdict: ✅ Source Safe

Quality Score: 78/100

Strengths

• Clean onchainos integration: All write operations correctly use onchainos wallet contract-call — no self-implemented signing or broadcasting
• Well-structured code: Clear separation between config, RPC, onchainos integration, and command modules
• Good DeFi UX: Two-step confirmation, dry-run mode, auto-quoting for liquidity, automatic pool selection (volatile vs stable)

Issues Found

• 🟡 Important: Unlimited token approvals (u128::MAX) without user warning — SKILL.md should warn about unlimited approvals and suggest limited approvals as an option
• 🟡 Important: The --force flag is always passed to onchainos wallet contract-call when --confirm is set, which bypasses onchainos's own confirmation prompts. This is by design for automation but could be dangerous if the agent calls --confirm without genuine user confirmation
• 🔵 Minor: No recommendation to run onchainos security token-scan before swapping to unknown tokens
• 🔵 Minor: RPC URL is hardcoded with no fallback mechanism — if publicnode.com is down, all operations fail
• 🔵 Minor: The get_allowance and get_balance parsing truncates to last 32 hex chars which could silently produce wrong results for malformed RPC responses (though unlikely in practice)

1. Add unlimited approval warning: In SKILL.md, add a security note warning users that token approvals are unlimited (type(uint256).max). Consider offering a flag for limited approvals (exact amount needed).

2. Clarify --confirm vs --force semantics: Document clearly that --confirm triggers --force on onchainos, and that the agent MUST have explicit user confirmation before passing --confirm. Consider renaming to avoid confusion with onchainos's own --force flag.

3. Add security scan recommendation: Before swap commands, recommend running onchainos security token-scan for unknown tokens, similar to how okx-dex-swap documents pre-swap security checks.

4. Add amount sanity checks: Consider adding warnings for unusually large transactions or high slippage settings to protect users from accidental large trades.

5. Add RPC fallback: Consider allowing the RPC URL to be configurable via environment variable or fallback to alternative public Optimism RPC endpoints.

6. Improve error messages: When RPC calls fail or return unexpected data, provide more actionable error messages (e.g., suggest checking network connectivity or trying again).

One-line verdict: Well-implemented Velodrome V2 DeFi plugin with correct onchainos integration for all write operations; needs minor security documentation improvements around unlimited approvals and pre-swap token scanning.

Merge recommendation: ⚠️ Merge with noted caveats

Items to address before or shortly after merge:

1. Add explicit warning about unlimited token approvals in SKILL.md Security Notices section
2. Clarify in SKILL.md that --confirm must only be used after genuine user confirmation (not agent auto-confirmation)
3. Consider adding a note recommending onchainos security token-scan before swapping unknown tokens